I am sorry, I could not find test cases. So, I didn't start anything new for the same

Hi mate. I believe you want to add the addition of a HTTP header "User-Agent" to the request options. You can leave the AGENT stuff alone (that is for something else, reusing TLS connections but issue #264 is different)

So add standard http header "User-Agent" with value "authorization-at-edge" or so to the options object (RequestOptions)

I'm sorry. I misunderstood the issue. Thanks for pointing in the right direction. I updated the PR.

Cheers mate and no worries! Easy to make mistakes

Having looked around a bit, I see the usual format for User-Agent is name/version, e.g. curl/7.64.1 or PostmanRuntime/7.26.5

I like adding the Auth@Edge version in there, so that we e.g. get authorization-at-edge/2.3.0, but it will mean that the Lambda@Edge functions need to know this version. We can make them know, because it is a CloudFormation parameter, that we can inject in the config (in the relevant Custom::LambdaCodeUpdate entries in the CFN template).

If you're up to adding that, go for it.

If that's a bit too much I can understand too let me know.

Question: did you test it like this? Does this indeed work to not run into the WAF rule?